Skip to content

chore: use release backends for cargo tools - #709

Merged
jdx merged 2 commits into
mainfrom
codex/use-release-backends
Jul 6, 2026
Merged

chore: use release backends for cargo tools#709
jdx merged 2 commits into
mainfrom
codex/use-release-backends

Conversation

@jdx

@jdx jdx commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • replace cargo:cargo-insta with aqua:mitsuhiko/insta
  • replace cargo:cargo-release with github:crate-ci/cargo-release
  • replace cargo:cargo-semver-checks with github:obi1kenobi/cargo-semver-checks
  • replace cargo:git-cliff with aqua:orhun/git-cliff
  • keep cargo-binstall because cargo:cargo-edit still uses the cargo backend

Validation

  • mise install smoke tests for the new GitHub/aqua specs in an isolated mise data dir
  • mise -C . ls

Note

Low Risk
Dev-environment and lockfile-only changes; no application runtime code, with the same tool versions and CLI entrypoints for existing mise tasks.

Overview
Switches four dev tools in mise.toml from cargo: installs to prebuilt release backends, with a matching mise.lock refresh (per-platform checksums and download URLs).

cargo:cargo-insta, cargo:cargo-release, cargo:cargo-semver-checks, and cargo:git-cliff are removed and replaced by aqua:mitsuhiko/insta, github:crate-ci/cargo-release, github:obi1kenobi/cargo-semver-checks, and aqua:orhun/git-cliff at the same versions where applicable. cargo:cargo-edit and cargo-binstall are unchanged so the remaining cargo-backed tool can still be installed.

Existing mise tasks (snapshots, release, lint:semver) still invoke the same binaries (cargo insta, cargo release, etc.); only how mise fetches them changes.

Reviewed by Cursor Bugbot for commit 56ddf41. Bugbot is set up for automated code reviews on this repo. Configure here.

@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jdx, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 68e2f6ab-f1be-4c84-962e-9d4b4e35876a

📥 Commits

Reviewing files that changed from the base of the PR and between 7e05325 and 56ddf41.

⛔ Files ignored due to path filters (1)
  • mise.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • mise.toml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR migrates four developer tool entries in mise.toml from the cargo: compile-from-source backend to prebuilt binary backends (aqua: and github:), eliminating the need to compile those tools locally. Tool versions are unchanged.

  • cargo:cargo-instaaqua:mitsuhiko/insta (v1.48.0)
  • cargo:cargo-releasegithub:crate-ci/cargo-release (v1.1.2)
  • cargo:cargo-semver-checksgithub:obi1kenobi/cargo-semver-checks (v0.48.0)
  • cargo:git-cliffaqua:orhun/git-cliff (v2.13.1)
  • cargo-binstall and cargo:cargo-edit are intentionally kept unchanged as cargo-edit still needs the cargo backend.

Confidence Score: 5/5

Safe to merge — only developer tooling specs are changed, no application or runtime code is affected.

All changes are confined to mise.toml and its generated lock file. The four tool specs switch from compile-from-source cargo backends to prebuilt binary backends while preserving the same tool versions. The lock file includes SHA-256 checksums for every platform, providing integrity verification. No CI workflows, Rust source, or other project files are touched.

No files require special attention.

Important Files Changed

Filename Overview
mise.toml Swaps four tool specs from cargo: to aqua: or github: backends; no version changes, only backend source changes
mise.lock Lock file regenerated with platform-specific checksums and URLs for the four newly-specified backends; old cargo entries removed

Reviews (2): Last reviewed commit: "chore(deps): update mise lockfile for re..." | Re-trigger Greptile

@jdx
jdx merged commit 466fbd6 into main Jul 6, 2026
6 checks passed
@jdx
jdx deleted the codex/use-release-backends branch July 6, 2026 19:43
@mise-en-dev mise-en-dev mentioned this pull request Jul 6, 2026
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Jul 9, 2026
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [usage](https://github.com/jdx/usage) | patch | `3.5.2` → `3.5.4` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>jdx/usage (usage)</summary>

### [`v3.5.4`](https://github.com/jdx/usage/blob/HEAD/CHANGELOG.md#354---2026-07-06)

[Compare Source](jdx/usage@v3.5.3...v3.5.4)

##### 🐛 Bug Fixes

- **(complete)** skip unreadable files in fish shebang completion scan by [@&#8203;GrantD-ADSK](https://github.com/GrantD-ADSK) in [#&#8203;707](jdx/usage#707)

##### 🔍 Other Changes

- Enable Entire for Codex by [@&#8203;jdx](https://github.com/jdx) in [#&#8203;695](jdx/usage#695)
- Update sponsor references for jdx.dev by [@&#8203;jdx](https://github.com/jdx) in [#&#8203;702](jdx/usage#702)
- use release backends for cargo tools by [@&#8203;jdx](https://github.com/jdx) in [#&#8203;709](jdx/usage#709)

##### 📦️ Dependency Updates

- update jdx/mise-action action to v4.2.0 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;698](jdx/usage#698)
- update rust-lang/crates-io-auth-action action to v1.0.5 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;697](jdx/usage#697)
- update rust crate itertools to 0.15 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;699](jdx/usage#699)
- update actions/checkout action to v7 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;700](jdx/usage#700)
- lock file maintenance by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;701](jdx/usage#701)
- update zizmorcore/zizmor-action action to v0.5.7 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;704](jdx/usage#704)
- update dependency cargo-binstall to v1.20.1 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;703](jdx/usage#703)
- update rust crate tera to v2 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;705](jdx/usage#705)
- lock file maintenance by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;708](jdx/usage#708)

##### New Contributors

- [@&#8203;GrantD-ADSK](https://github.com/GrantD-ADSK) made their first contribution in [#&#8203;707](jdx/usage#707)

### [`v3.5.3`](https://github.com/jdx/usage/blob/HEAD/CHANGELOG.md#353---2026-06-23)

[Compare Source](jdx/usage@v3.5.2...v3.5.3)

##### 🐛 Bug Fixes

- **(docs)** show negated flags in cli help by [@&#8203;jdx](https://github.com/jdx) in [#&#8203;694](jdx/usage#694)
- **(zsh)** preserve options for default completion by [@&#8203;jdx](https://github.com/jdx) in [#&#8203;693](jdx/usage#693)

##### 📦️ Dependency Updates

- update jdx/pr-closer action to v1.1.0 by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;689](jdx/usage#689)
- lock file maintenance lockfile maintenance by [@&#8203;renovate\[bot\]](https://github.com/renovate\[bot]) in [#&#8203;691](jdx/usage#691)

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTYuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI1Ni4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiLCJhdXRvbWF0aW9uOmJvdC1hdXRob3JlZCIsImRlcGVuZGVuY3ktdHlwZTo6cGF0Y2giXX0=-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant